IRIX 5.3 for Indy R4400

home *** CD-ROM | disk | FTP | other *** search

/ IRIX 5.3 for Indy R4400 / IRIX 5.3 for Indy R4400 175MHz.img / relnotes / FDDIXPress / ch2.z / ch2

Wrap

Text File | 1995-02-28 | 31KB | 791 lines

- 1 - 2. _I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n This chapter provides information about installing FDDIXPress software. The information listed here is product-specific; for general information about installing software, refer to the _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e and _P_e_r_s_o_n_a_l _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. The FDDIXPress product consists of a hardware component and a software component. The hardware component is an FDDI board; the software is on the CD-ROM. To install the product, follow the procedures in the overview below. The procedures must be followed in the order they are listed. 1. Install the software, using the instructions in this document in Section 2.2, ``Installing FDDIXPress Software.'' 2. Configure the software, using the instructions in section 2.3, ``Configuring the FDDIXPress Software.'' 3. Install the board, using the board's installation guide, or have an authorized field service engineer install the board using the field service installation instructions. 4. Configure your FDDI station's environment to be user- friendly, using the instructions in the section ``Configuring the Environment for User-Friendliness and Safety,'' in Chapter 2 of the _F_D_D_I_X_P_r_e_s_s _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. 5. Verify the FDDI connection, using the instructions in the section ``Verifying the FDDI Connection,'' in Chapter 2 of the _F_D_D_I_X_P_r_e_s_s _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. 2.1 _G_e_n_e_r_a_l__I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n This section contains general information about the FDDIXPress software. This information is useful during installation and configuration. 2.1.1 _F_D_D_I__N_e_t_w_o_r_k__I_n_t_e_r_f_a_c_e__N_a_m_e_s Each type of FDDIXPress board has its own network interface software. During development, each network interface is given a name. The FDDI interface names that have been shipped with this release are specified below: _x_p_i# for IRIS Indigo, Indigo, and CHALLENGE M platforms. (The first FDDIXPress board found is assigned the name _x_p_i_0. The second board is - 2 - assigned the name _x_p_i_1. On Indigo and CHALLENGE M machines, the system searches for the FDDIXPress boards in the GIO option slots in the following order: top slot first, middle slot second, bottom slot last.) _i_p_g# for VMEbus systems, including CHALLENGE L, CHALLENGE XL, POWER Series, Professional Series, IRIS Crimson, and Personal IRIS platforms. The board's jumper-configured unit number determines the final number on the interface name (for example, _i_p_g_0, _i_p_g_1, _i_p_g_2, etc.). 2.1.2 _F_D_D_I_X_P_r_e_s_s__S_u_b_s_y_s_t_e_m_s Following is a description of the FDDIXPress subsystems: _F_D_D_I_X_P_r_e_s_s._s_w._F_D_D_I_X_P_r_e_s_s FDDIXPress software: driver, utilities, SMT daemon, and miscellaneous files. _F_D_D_I_X_P_r_e_s_s._m_a_n._F_D_D_I_X_P_r_e_s_s Manual pages for FDDIXPress utilities and SMT daemon. _F_D_D_I_X_P_r_e_s_s._m_a_n._r_e_l_n_o_t_e_s These release notes. 2.1.3 _F_D_D_I_X_P_r_e_s_s__S_u_b_s_y_s_t_e_m__D_i_s_k__S_p_a_c_e__R_e_q_u_i_r_e_m_e_n_t_s This section lists the FDDIXPress subsystems and their sizes. All these subsystems are installed when you use the install FDDIXPress and go commands of _i_n_s_t. Note: The listed subsystem sizes are approximate. Refer to the _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e for information on determining exact sizes. Subsystem Name Subsystem Size (512-byte blocks) _F_D_D_I_X_P_r_e_s_s._s_w._F_D_D_I_X_P_r_e_s_s 1980 _F_D_D_I_X_P_r_e_s_s._m_a_n._F_D_D_I_X_P_r_e_s_s 38 _F_D_D_I_X_P_r_e_s_s._m_a_n._r_e_l_n_o_t_e_s 30 2.1.4 _I_n_s_t_a_l_l_a_t_i_o_n__M_e_t_h_o_d All of the subsystems for FDDIXPress can be installed using the IRIX installation method. You do not need to use the miniroot, although you may do so, if convenient as part of an operating system upgrade. Refer to the _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e or the installation instructions in the _P_e_r_s_o_n_a_l _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e for complete installation instructions. - 3 - Note: The FDDIXPress driver will not function until three additional steps are completed: (1) the board is installed, (2) the operating system is rebuilt, by restarting the system or using the _a_u_t_o_c_o_n_f_i_g command, and (3) the system is rebooted. 2.1.5 _C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s The files listed below are used by FDDIXPress software. Editing these files is not required during initial installation and configuration of FDDIXPress, but may be desirable at some point in time for customization of the FDDI environment. /_u_s_r/_e_t_c/_f_d_d_i/_s_m_t_d._c_o_n_fSMT daemon configuration file. Experienced FDDI system administrators may want to edit this file. /_u_s_r/_e_t_c/_f_d_d_i/_s_m_t_d._m_i_bManagement Information Base file. This file should never be edited. /_u_s_r/_s_y_s_g_e_n/_m_a_s_t_e_r._d/_i_f__i_p_gIPG driver configuration file. File for enabling/disabling a number of _i_p_g driver flags. /_u_s_r/_s_y_s_g_e_n/_m_a_s_t_e_r._d/_i_f__x_p_iXPI driver configuration file. File for enabling/disabling a number of _x_p_i driver flags. 2.2 _I_n_s_t_a_l_l_i_n_g__F_D_D_I_X_P_r_e_s_s__S_o_f_t_w_a_r_e This section describes how to install FDDIXPress software. Before starting the installation, use the command below to verify that FDDIXPress is not already installed. For example, FDDIXPress may have been installed at the same time as the operating system. % versions FDDIXPress If the display indicates that FDDIXPress 3.6 is installed, you can skip the software installation procedure and proceed to the configuration. Otherwise, follow the instructions below to install FDDIXPress. 2.2.1 _P_r_e_r_e_q_u_i_s_i_t_e_s Your system must be running IRIX release 5.3. To verify the release your system is currently running, use the command below: % versions eoe1 I eoe1 _d_a_t_e _E_x_e_c_u_t_i_o_n _O_n_l_y _E_n_v_i_r_o_n_m_e_n_t _1, _5._3 - 4 - 2.2.2 _P_r_e_p_a_r_i_n_g__f_o_r__I_n_s_t_a_l_l_a_t_i_o_n 1. Determine the installation method. There are four methods for installing the FDDIXPress software: from a local peripheral device, from a remote peripheral device, from a remote Ethernet boot server (distribution directory), from a local distribution directory. These methods are summarized and explained in Chapter 4 of the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e, where Table 4-1 provides an excellent overview. Note: ``Local'' refers to connecting the CD-ROM (or tape) player directly to the target system (the system onto which you are installing software). ``Remote'' refers to loading the software over the target system's Ethernet network connection using a CD-ROM (or tape) device connected to a different Ethernet station. In order to install FDDIXPress software from a remote distribution directory, your system must be physically connected to the Ethernet and it must have a functioning Ethernet connection. 2. Locate the following items: - For installation from a peripheral device, locate the CD-ROM disk containing FDDIXPress software. If you specially ordered another medium (for example, tape), locate that item. - For installation from a peripheral device, locate a device to play (read) the CD-ROM or tape. This device is not shipped with the FDDIXPress product; it belongs to your site. - For installation from a distribution directory, determine the host name of the Ethernet station and the path to the directory. 3. Set up the installation hardware. - If you are using a local device, follow the instructions in your system's owner's guide to connect the peripheral device. - If you are using a remote device, follow the remote workstation or server's instructions for attaching peripheral devices. - 5 - - For installation from a distribution directory, verify that FDDIXPress has been loaded onto the station. A section of the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e provides instructions on preparing distribution directories. 2.2.3 _I_n_s_t_a_l_l_i_n_g__t_h_e__S_o_f_t_w_a_r_e Use the IRIX installation method to install the FDDIXPress software. Step-by-step instructions are provided below. Note: More detailed explanations about the IRIX installation method are located in the _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e and the _P_e_r_s_o_n_a_l _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. 1. In a shell window, become superuser: % su Password: _t_h_e_p_a_s_s_w_o_r_d # 2. Invoke the _i_n_s_t utility with the command below: # inst {the _i_n_s_t menu appears} Inst> 3. When the _i_n_s_t prompt appears (Inst>), use the from command to indicate the location of FDDIXPress software. Table 10-2 in the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e summarizes the entries for this command. The command below can be used when the location is a local CD-ROM: Inst> from /CDROM/dist 4. When you are ready to install FDDIXPress, use the command below to prepare for installation: Inst> install FDDIXPress 5. Then use the command below to install the software: Inst> go 6. When the installation completes successfully, quit: Inst> quit 7. Follow the steps in Section 2.3, ``Configuring the FDDIXPress Software.'' - 6 - 2.3 _C_o_n_f_i_g_u_r_i_n_g__t_h_e__F_D_D_I_X_P_r_e_s_s__S_o_f_t_w_a_r_e This section describes the quickest, easiest method to configure a new FDDI network connection for the scenarios in the bulleted list below. If your system has a configuration that is not covered, follow the instructions in the _F_D_D_I_X_P_r_e_s_s _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. It is highly recommended that the FDDIXPress configuration procedure be done before installing the FDDIXPress board. If you install the board and restart the system without configuring the FDDIXPress software, the FDDI connection will not function when the system comes up. If the system also has an Ethernet connection, the Ethernet will not function either. Note: The instructions in this section assume that the system already has (or has had) a functional Ethernet connection. If this is not the case, follow the instructions in the _P_e_r_s_o_n_a_l _S_y_s_t_e_m _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e or the _A_d_v_a_n_c_e_d _S_i_t_e _a_n_d _S_e_r_v_e_r _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e to configure the system for networking (giving it a host name, IP address, etc.). This section is divided into three configuration scenarios. Select the one that is appropriate. +o FDDI as the primary network interface with Ethernet as the secondary. This configuration is recommended for stations with two network connections and a disk. +o FDDI as the secondary network interface with Ethernet as the primary. This configuration is recommended for a diskless workstation. +o FDDI as the only network connection. Note: The procedures described in the following sections configure a basic non-personalized FDDI network connection. If you need or want to configure site- specific items, follow the instructions in Chapter 2 of the _F_D_D_I_X_P_r_e_s_s _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e, either now (instead of the instructions provided here) or after you have used the instructions here to get the system up and running. - 7 - 2.3.0.1 _C_o_n_f_i_g_u_r_i_n_g _F_D_D_I _a_s _P_r_i_m_a_r_y _a_n_d _E_t_h_e_r_n_e_t _a_s _S_e_c_o_n_d_a_r_y This section provides instructions to set up your system so the FDDI connection serves as the primary network interface and Ethernet is the secondary network interface. This configuration is the easiest to do and provides the best performance. Note: If your site uses an NIS service, the changes to the /_e_t_c/_h_o_s_t_s file described in this section must also be made to the hosts database on the NIS server. 1. If you are not superuser, type su to become superuser (_r_o_o_t): % su Password: _t_h_e_p_a_s_s_w_o_r_d # 2. Determine your station's host name: # hostname 3. Use your favorite editor to open the /_e_t_c/_h_o_s_t_s file. To open the file with _j_o_t, use the line below: # /usr/sbin/jot /etc/hosts 4. Find the line with your station's host name. 5. Copy this line. Paste the copy below the original. 6. Return to the original line. Change the address (digits on the left) to the IP address for the FDDI network. This line configures your station's FDDI network interface. Do not change the host name. Note: IP addresses are usually assigned by a site's network administrator (who has obtained the addresses from the Network Information Center). The network portion of the IP address for each local area network must be unique; you cannot use the same network address for your system's Ethernet and FDDI connections. For further information, see the section on choosing an IP address in the _I_R_I_X _A_d_v_a_n_c_e_d _S_i_t_e _a_n_d _S_e_r_v_e_r _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. 7. Go to the new line. Change each instance of your station's _h_o_s_t_n_a_m_e to ``gate-_h_o_s_t_n_a_m_e''. This line configures your station's Ethernet network interface. Note: Do not change the IP address on the new line (representing the Ethernet connection.) - 8 - For example, if you were creating entries for a station with a host name of _m_i_c_k_e_y residing in the domain _d_i_s_n_e_y._c_o_m, you would now have the following two lines in the /_e_t_c/_h_o_s_t_s file, where each x can be one to three digits: x.x.x.x mickey.disney.commickey#FDDI primary x.x.x.x gate-mickey.disney.comgate-mickey#Ether secondary 8. Save and close the file. 9. The system is now ready to have its FDDIXPress board installed. Either follow the instructions in the FDDIXPress board's installation guide to install the board, or have an authorized field service engineer install the board using the field service installation instructions. Note: If the board is already installed, restart the system, rebuild the operating system by answering yes when prompted, then restart the system a second time. 2.3.0.2 _C_o_n_f_i_g_u_r_i_n_g _F_D_D_I _a_s _S_e_c_o_n_d_a_r_y _a_n_d _E_t_h_e_r_n_e_t _a_s _P_r_i_m_a_r_y This section provides instructions to configure your system so the FDDI connection serves as the secondary network interface and Ethernet is the primary one. This configuration is recommended for diskless workstations. When FDDI is the secondary interface, the system does not make the most efficient use of the FDDI connection. For workstations with disks, it is recommended that the FDDI network interface be configured as the primary interface. 1. If you are not superuser, become superuser (_r_o_o_t): % su Password: _t_h_e_p_a_s_s_w_o_r_d # 2. Determine your station's host name. # hostname 3. Use your favorite editor to open the /_e_t_c/_h_o_s_t_s file. To open the file with _j_o_t, use the command below: # /usr/sbin/jot /etc/hosts 4. Find the line with your station's host name. This line configures your station's Ethernet network interface. 5. Copy this line. Paste the copy below the original. This new line configures your station's FDDI network interface. - 9 - 6. On the new line, change each instance of your station's _h_o_s_t_n_a_m_e to ``fddi-_h_o_s_t_n_a_m_e''. 7. On the same line, change the address (digits on the left) to the FDDI IP address. Note: IP addresses are usually assigned by a site's network administrator (who has obtained the addresses from the Network Information Center). The network portion of the IP address for each local area network must be unique; you cannot use the same network address for your system's Ethernet and FDDI connections. For further information, see the section on choosing an IP address in the _I_R_I_X _A_d_v_a_n_c_e_d _S_i_t_e _a_n_d _S_e_r_v_e_r _A_d_m_i_n_i_s_t_r_a_t_i_o_n _G_u_i_d_e. For example, if you were creating entries for a station with a host name of _m_i_n_n_i_e residing in the domain _d_i_s_n_e_y._c_o_m, you would have the following two lines in the /_e_t_c/_h_o_s_t_s file, where each x can be one to three digits: x.x.x.x minnie.disney.comminnie#Ether primary x.x.x.x fddi-minnie.disney.comfddi-minnie#FDDI secondary 8. Save and close the file. 9. Open the /_e_t_c/_c_o_n_f_i_g/_n_e_t_i_f._o_p_t_i_o_n_s file. To open the file with _j_o_t, use the command line below: # /usr/sbin/jot /etc/config/netif.options 10. Find the line below: : if1name= 11. Change the line to one of the following entries. Notice that the colon and leading space must be removed, and the name of the Ethernet interface must be the name of the interface currently installed on the station (for example, _e_c_0 is the built-in Ethernet interface for Indigo, IRIS Indigo, and Personal IRIS workstations). if1name=ec0 or if1name=_E_t_h_e_r_n_e_t_i_n_t_e_r_f_a_c_e 12. Find the line below: : if2name= 13. Edit the line to match one of the following lines. Notice that the colon and leading space must be - 10 - removed, and the name of the FDDI interface must be correct for the platform (for example, _x_p_i_0 for Indigo and IRIS Indigo workstations). if2name=xpi0 or if2name=ipg0 14. Find the line below: : if2addr=gate-$HOSTNAME 15. Edit the line to read as follows. Notice that the colon and leading space must be removed. if2addr=fddi-$HOSTNAME 16. Save and close the file. 17. The system is now ready to have its FDDIXPress board installed. Either follow the instructions in the board's installation guide to install the board, or have an authorized field service engineer install the board, using the field service installation instructions. Note: If the board is already installed, restart the system, rebuild the operating system by answering yes when prompted, then restart the system a second time. 2.3.0.3 _C_o_n_f_i_g_u_r_i_n_g__F_D_D_I__a_s__t_h_e__O_n_l_y__N_e_t_w_o_r_k__I_n_t_e_r_f_a_c_e This section provides instructions to set up your system with one network connection, an FDDI connection. 1. If you are not superuser, use the command below to become superuser (_r_o_o_t). % su Password: _t_h_e_p_a_s_s_w_o_r_d # 2. Determine your station's host name, using the command below: # hostname 3. Use your favorite editor to open the /_e_t_c/_h_o_s_t_s file. To open the file with _j_o_t, use the command below: # /usr/sbin/jot /etc/hosts 4. Find the line with your station's host name. 5. Change the address (digits on the left) to the IP address for the FDDI network. - 11 - For example, if you were making an entry for a station with a host name of _m_i_c_k_e_y residing in the domain _d_i_s_n_e_y._c_o_m with an FDDI IP address of 187.8.27.6, you would have created the following line in the /_e_t_c/_h_o_s_t_s file: 187.8.27.6 mickey.disney.commickey#FDDI 6. Save and close the file. 7. The system is now ready to have its FDDXPress board installed. Either follow the instructions in the board's installation guide to install the board, or have an authorized field service engineer install the board, using the field service installation instructions. Note: If the board is already installed, restart the system, rebuild the operating system by answering yes when prompted, then restart the system a second time. 2.4 _C_o_n_f_i_g_u_r_i_n_g__a__D_i_s_k_l_e_s_s__S_t_a_t_i_o_n A diskless FDDI station must be configured in accord with the guidelines in this section. 1. The station must have either two network interfaces (an Ethernet from which to boot and an FDDI) or a local CD-ROM player from which to boot and an FDDI interface. The remaining text and guidelines apply only to stations that boot over an Ethernet. A diskless workstation (client) must boot (from its server) over its Ethernet connection, hence, the diskless station must have both Ethernet and FDDI connections, if it wants to use resources on an FDDI network. Use the command below to display the station's network interfaces, then verify that one of the IP addresses in the display is for an Ethernet and one is for an FDDI local area network: % /usr/etc/netstat -in 2. The _n_e_t_a_d_d_r value in NVRAM must be an Ethernet IP address. The station's PROM must use the Ethernet connection for booting over the network. To verify that the system's PROM can access the Ethernet, use the commands below. The output from _n_e_t_a_d_d_r and the _i_n_e_t value must match. - 12 - % /etc/nvram netaddr _x_x_x._x_x_x._x_x_x._x_x_x % /_u_s_r/_e_t_c/_i_f_c_o_n_f_i_g _E_t_h_e_r_n_e_t_i_n_t_e_r_f_a_c_e . . . _i_n_e_t _x_x_x._x_x_x._x_x_x._x_x_x . . . 3. Ethernet must be configured as the primary network interface. Once the PROM has loaded the miniroot (bootstrap kernel) from the boot server, control is passed to the miniroot. At this point, the diskless client is known to the boot server by the IP address in the NVRAM. If this address were to change at this point, the server would become confused and the boot process would not complete. The best and easiest way to prevent this from happening is to configure Ethernet (and build the miniroot with Ethernet) as the primary network interface. To verify that Ethernet is configured as the primary network interface and FDDI is the secondary, use the commands below, where _E_t_h_e_r_n_e_t_i_n_t_e_r_f_a_c_e is ec0, enp0, et0, or another Ethernet interface and _F_D_D_I_i_n_t_e_r_f_a_c_e is ipg# or xpi#: # /bin/grep if1name /etc/config/netif.options ... if1name=_E_t_h_e_r_n_e_t_i_n_t_e_r_f_a_c_e # /bin/grep if2name /etc/config/netif.options ... if2name=_F_D_D_I_i_n_t_e_r_f_a_c_e Note: Once the miniroot is in control, the booting procedure is completed using NFSr over the network interface that the station's route daemon indicates is the shortest path to the boot server. If you want booting to complete over the FDDI network, use a _r_o_u_t_e command in a configuration file to force the route daemon (_r_o_u_t_e_d) to believe that the shortest route to the boot server is over the FDDI network interface. See the man pages for _r_o_u_t_e_d(1M) and _r_o_u_t_e(1M) for details.